-
Notifications
You must be signed in to change notification settings - Fork 727
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PCBB] Add testcases to verify separated DSCP_TO_TC_MAP
on leaf router
#6393
[PCBB] Add testcases to verify separated DSCP_TO_TC_MAP
on leaf router
#6393
Conversation
This pull request introduces 3 alerts when merging 3c33c95 into 0558e61 - view on LGTM.com new alerts:
|
@stephenxs Can you please help review this PR? |
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
This pull request introduces 3 alerts when merging 68880b8 into b3623be - view on LGTM.com new alerts:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We plan to have different DSCP_TO_TC mapping on downlink/uplink ports in t0 as well. so hardcoding AZURE_DOWNLINK
is probably not good.
The rest LGTM.
|
||
|
||
def separated_dscp_to_tc_map_on_uplink(duthost): | ||
""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can make it more generic by adding an argument for the expected map name?
Eg., in dual ToR t0 scenario, maybe AZURE_DOWNLINK
will be introduced for downlink ports (sonic-net/sonic-buildimage#12605).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated. Now the code counts the dscp_to_tc_map
for each port.
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
This pull request introduces 5 alerts when merging c5fa8af into a1c1ddb - view on LGTM.com new alerts:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@bingwang-ms There are conflicts cherry-picking this PR to 202012 branch. Can you help create a separate PR to the 202012 branch? |
…ter (#6393) * Add testcases to verify separated DSCP_TO_TC_MAP on T1
Open another PR #6817 to backport the change into |
What is the motivation for this PR? This PR is to backport PR #6393 into 202012 branch. This PR is to add two new test cases testQosSaiSeparatedDscpQueueMapping and testQosSaiSeparatedDscpToPgMapping to verify separated DSCP_TO_TC_MAP for uplink and downlink on T1. Code change in sonic-buildimage sonic-net/sonic-buildimage#11569 How did you do it? Swap syncd docker to syncd-rpc Generate traffic with various DSCP value, and send the packet to DUT from uplink ports or downlink ports Check the increment in each PG and Queue with SAI rpc call. How did you verify/test it? Verified on a TH2 device ``` collected 2 items qos/test_qos_sai.py::TestQosSai::testQosSaiSeparatedDscpQueueMapping[str-7260cx3-acs-7-None-downstream] PASSED [ 50%] qos/test_qos_sai.py::TestQosSai::testQosSaiSeparatedDscpQueueMapping[str-7260cx3-acs-7-None-upstream] PASSED [100%] collected 2 items qos/test_qos_sai.py::TestQosSai::testQosSaiSeparatedDscpToPgMapping[str-7260cx3-acs-7-None-downstream] PASSED [ 50%] qos/test_qos_sai.py::TestQosSai::testQosSaiSeparatedDscpToPgMapping[str-7260cx3-acs-7-None-upstream] PASSED [100%] ``` Any platform specific information? No. Supported testbed topology if it's a new test case? T1 specific test cases.
Description of PR
Summary:
This PR is to add two new test cases
testQosSaiSeparatedDscpQueueMapping
andtestQosSaiSeparatedDscpToPgMapping
to verify separatedDSCP_TO_TC_MAP
for uplink and downlink on T1.Code change in sonic-buildimage sonic-net/sonic-buildimage#11569
Type of change
Back port request
Approach
What is the motivation for this PR?
This PR is to add two new test cases
testQosSaiSeparatedDscpQueueMapping
andtestQosSaiSeparatedDscpToPgMapping
to verify separatedDSCP_TO_TC_MAP
for uplink and downlink on T1.How did you do it?
How did you verify/test it?
Verified on a TH2 device
Any platform specific information?
No.
Supported testbed topology if it's a new test case?
T1 specific test cases.
Documentation